Modified the bundle script and its helper scripts to include integtests from python-only packages#326
Modified the bundle script and its helper scripts to include integtests from python-only packages#326bieryAtFnal wants to merge 3 commits into
Conversation
…ython-only packages with integtests.
|
I checked the given commands and they work as advertised as described in the above script. One issue I bumped into, however - the line: |
…of finding 'local' python packages
|
I have modified the |
|
I've confirmed both just from looking at the |
jcfreeman2
left a comment
There was a problem hiding this comment.
See comment I left a moment ago.
Description
Now that we have integration tests from Python packages installed in the
.venvdirectory of software areas, we can proceed to include them in the global bundle script and its helper scripts:dunedaq_integtest_bundle.shlist_available_integtests.shlist_repos_with_integtests.shThe changes in this Pull Request attempt to do that.
Two notes:
pythoncodesubdirectory. (Typically, all Python packages are installed in the.venvsubdirectory of a local software area, so the presence of a package in that area can't be used to determine "local" vs. not-local.)-p no:cacheproviderqualifier to thepytestcommand when running integtests from Python packages that are not installed in a write-able location on disk. The reason for this is twofold: there are discussions about how to avoid needing to specify that qualifier, so we will let that discussion proceed. And in the short term, I expect that it will be rather rare for someone to run integtests from Python packages without having a local software area.Here are suggested steps for testing these changes:
Type of change
Testing checklist
dunedaq_integtest_bundle.sh)Further checks